[frontend] Migrate CK Editor to 9.3 (#8151) #8787
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Landry Trebon <[email protected]>
github-actions
bot
added
the
filigran team
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #8787 +/- ##
==========================================
- Coverage 66.29% 66.29% -0.01%
==========================================
Files 597 597
Lines 60958 60958
Branches 6261 6264 +3
==========================================
- Hits 40414 40412 -2
- Misses 20544 20546 +2 ☔ View full report in Codecov by Sentry. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update CKEditor to fix security issues
https://app.snyk.io/vuln/SNYK-JS-MICROMATCH-6838728
https://app.snyk.io/vuln/SNYK-JS-SERIALIZEJAVASCRIPT-6147607
This PR cherry-picks the update from release/6.4 as we want to deliver this fix earlier.
see #8151